{"schema_version":"1.7.5","id":"CVE-2021-47583","published":"2024-06-19T15:15:52.843Z","modified":"2026-03-15T22:43:16.000373Z","related":["SUSE-SU-2024:2362-1","SUSE-SU-2024:2365-1","SUSE-SU-2024:2372-1","SUSE-SU-2024:2384-1","SUSE-SU-2024:2394-1","SUSE-SU-2024:2902-1","SUSE-SU-2024:2929-1","SUSE-SU-2024:2939-1"],"details":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: mxl111sf: change mutex_init() location\n\nSyzbot reported, that mxl111sf_ctrl_msg() uses uninitialized\nmutex. The problem was in wrong mutex_init() location.\n\nPrevious mutex_init(&state->msg_lock) call was in ->init() function, but\ndvb_usbv2_init() has this order of calls:\n\n\tdvb_usbv2_init()\n\t  dvb_usbv2_adapter_init()\n\t    dvb_usbv2_adapter_frontend_init()\n\t      props->frontend_attach()\n\n\t  props->init()\n\nSince mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach()\ninternally we need to initialize state->msg_lock before\nfrontend_attach(). To achieve it, ->probe() call added to all mxl111sf_*\ndevices, which will simply initiaize mutex.","affected":[{"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47583.json","unresolved_ranges":[{"events":[{"introduced":"3.7"},{"fixed":"4.19.222"}]},{"events":[{"introduced":"4.20"},{"fixed":"5.4.168"}]},{"events":[{"introduced":"5.5"},{"fixed":"5.10.88"}]},{"events":[{"introduced":"5.11"},{"fixed":"5.15.11"}]}]}}],"references":[{"type":"FIX","url":"https://git.kernel.org/stable/c/b99bdf127af91d53919e96292c05f737c45ea59a"},{"type":"FIX","url":"https://git.kernel.org/stable/c/44870a9e7a3c24acbb3f888b2a7cc22c9bdf7e7f"},{"type":"FIX","url":"https://git.kernel.org/stable/c/4b2d9600b31f9ba7adbc9f3c54a068615d27b390"},{"type":"FIX","url":"https://git.kernel.org/stable/c/8c6fdf62bfe1bc72bfceeaf832ef7499c7ed09ba"},{"type":"FIX","url":"https://git.kernel.org/stable/c/96f182c9f48b984447741f054ec301fdc8517035"}],"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}